Return-link routing in a hybrid network

ABSTRACT

Embodiments provide techniques for providing return-link routing in a hybrid communications network that includes a number of different networks having different characteristics. User terminal routing systems (UTRSs) provide interfaces between local user networks and the multiple communications networks of the hybrid network. Each UTRS can include a routing table having stored mappings that are populated according to forward-link communications (implicitly or explicitly), each associating a respective one of a plurality of routing table entries with one of the communications networks. When a UTRS receives return-link data from its respective local user network, the received data indicates a destination node. The UTRS can determine which of the stored mappings corresponds to the destination node and can route the received return-link data over a selected one of the communications networks in accordance with the identified one of the mappings.

RELATED APPLICATIONS

This application is a Continuation of U.S. patent application Ser. No.15/592,097 filed on May 10, 2017 entitled “RETURN-LINK ROUTING IN AHYBRID NETWORK”, which claims the benefit of U.S. Pat. Prov. App. No.62/433,689 filed on Dec. 13, 2016, the entirety of which is incorporatedherein by reference.

FIELD

Embodiments relate generally to communications systems, and, moreparticularly, to routing of return-link traffic in a hybridcommunications network.

BACKGROUND

Many communications networks have large numbers of user that interfacewith the networks via large numbers of user terminals. It can bedesirable in such networks for the user terminals to be implemented atrelatively low cost and with relatively low complexity. Some moderncommunications environments include hybrid networks, in which the userterminals are in communication with multiple different types of networkshaving different characteristics. For example, the hybrid network caninclude one or more higher-throughput, higher-latency networks (e.g., asatellite network) and one or more lower-throughput, lower-latencynetworks (e.g., a cable network, a cellular network, etc.). Routingdifferent traffic flows over the different networks can more efficientlyutilize the overall resources of the hybrid network. However,determining which of the networks to use for each traffic flow (e.g., inreal time) can be computationally intensive. While provider-side nodesof the network (e.g., gateways, core nodes, etc.) can include sufficientprocessing capability to make such determinations for forward-linktraffic, the user terminals may not have sufficient processingcapability to make such determinations for return-link traffic.

BRIEF SUMMARY

Among other things, systems and methods are described for providingreturn-link routing in a hybrid communications network. The hybridcommunications network includes a number of different networks havingdifferent characteristics (e.g., different latencies, differentthroughput, different user cost per bit, etc.). Users can interface withthe hybrid network via respective user terminals that include userterminal routing systems. For example, each user terminal routing systemprovides an interface between a local user network (e.g., providinglocal communications with one or more consumer premises equipment (CPE)devices) and the multiple communications networks of the hybrid network.Each user terminal routing system can include a routing table havingstored thereon multiple mappings. The mappings are populated accordingto forward-link communications received via at least one of thenetworks, and each mapping associates a respective one of a plurality ofrouting table entries with one of the communications networks. Eachrouting table entry identifies at least a forward-link content source(FLCS) identifier, for example, as part of a routing tuple, or the like.When a user terminal routing system receives return-link data from itsrespective local user network, the received return-link data indicates adestination node. The user terminal routing system can determine whichof the stored mappings has a FLCS identifier that corresponds to (e.g.,matches) the destination node, and the user terminal routing system canroute the received return-link data over a selected one of thecommunications networks in accordance with the identified one of themappings.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is described in conjunction with the appendedfigures:

FIG. 1 shows an illustrative hybrid communications environment, as acontext for various embodiments;

FIGS. 2A-2C show a first set of examples in which return-link routingdeterminations are made by a user terminal in a hybrid communicationsenvironment;

FIG. 3 shows a second example in which return-link routingdeterminations are made by a user terminal in a hybrid communicationsenvironment;

FIG. 4 shows a block diagram of a user terminal environment, includingan illustrative user terminal in communication with a local user networkand a hybrid communications network, according to various embodiments;and

FIG. 5 shows a flow diagram of an illustrative method for return-linkrouting by a user terminal in a hybrid networking environment, accordingto various embodiments.

In the appended figures, similar components and/or features can have thesame reference label. Further, various components of the same type canbe distinguished by following the reference label by a second label thatdistinguishes among the similar components. If only the first referencelabel is used in the specification, the description is applicable to anyone of the similar components having the same first reference labelirrespective of the second reference label.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth toprovide a thorough understanding of the present invention. However, onehaving ordinary skill in the art should recognize that the invention canbe practiced without these specific details. In some instances,circuits, structures, and techniques have not been shown in detail toavoid obscuring the present invention.

FIG. 1 shows an illustrative hybrid communications environment 100, as acontext for various embodiments. As illustrated, the hybridcommunications environment 100 includes a number of user terminals 110in communications with at least one provider-side network node 150 via ahybrid communications network 130. The hybrid communications network 130includes a number of communications networks 132 that provide differentnetwork characteristics. The communications networks 132 can include anysuitable types of networks for carrying different types of traffic andcan include wired, wireless, public, private, secure, unsecure, and/orother network links. For example, one of the communications networks 132can provide relatively high throughput with relatively high latency anda relatively high cost per bit. For example, the communications network132 can include a satellite link having a geosynchronous earth orbit(GEO) satellite, a medium earth orbit (MEO) satellite, a low earth orbitsatellite (LEO), etc. Another of the communications networks 132 canprovide relatively low throughput with relatively low latency and arelatively low cost per bit. For example, the communications network 132can include a terrestrial network, such as a digital subscriber line(DSL) network, a cable based network, a long-term evolution (LTE)wireless network, a cellular network, or the like. Alternatively, onecommunications network 132 can be a GEO satellite network, and anothercommunications network 132 cam be a MEO or LEO satellite network. Insome cases, multiple of the communications networks 132 of the hybridcommunications network 130 can have similar or identical networkcharacteristics.

The hybrid communications network 130 can provide communications betweenlocal user networks 105 and content networks 175 via the user terminals110, the communications networks 132, and the provider-side networknode(s) 150. Each local user network 105 can include one or moreconsumer premises equipment devices (CPEs) 102 that are coupled withtheir respective user terminal 110 via wired or wireless connections.For example, the user terminals 110 can include any suitable localnetwork interface 127, such as a wired and/or wireless router thatimplements a local area network. The CPEs 102 can be home or officecomputing devices, such as desktop computers, laptop computers, smartphones, tablet devices, Internet-enabled televisions or otherappliances, or the like. The content network(s) 175 can include anysuitable remote network, such as the Internet. As illustrated, thecontent network(s) 175 can include any suitable number of host computers172, such as content servers. The host computers 172 can host (orotherwise provide) any suitable type of content, such as audio and/orvideo file access, audio and/or video streaming service, voice overInternet protocol (VoIP) service, online gaming content, messaging(e.g., including control messages for the hybrid communications network130), etc. For example, users can subscribe to communications servicesand/or content services (e.g., Internet service), which they can accessover the hybrid communications network 130 via their CPEs 102.

In some embodiments, the user terminal 110 can include a hybrid networkinterface 125 for receiving forward-link data from, and transmittingreturn-link data to, the multiple communications networks 132 of thehybrid communications network 130. For example, as described below, theuser terminal 110 can include physical and/or logical ports 122, layer 3routing modules, forwarding modules (e.g., for forwarding through layer2 tunnels), and/or any other suitable components. The provider-sidenetwork node 150 can include a provider-side hybrid network interface145, including similar or different components for interfacing with thecommunications networks 132 of the hybrid communications network 130.For example, the provider-side hybrid network interface 145 can includephysical and/or logical ports 142, layer 3 routing modules, forwardingmodules, etc. The provider-side network node 150 can also include aprovider-side routing module 160 that makes routing determinations(e.g., forward-link routing determinations) for routing and/orforwarding traffic over the hybrid communications network 130. The caninclude data classifiers, and/or any other suitable components formaking routing determinations. For example, a data classifier in theprovider-side network node 150 classifies forward-link data destined fora CPE 102 and determines over which communications network 132 toforward the forward-link data in accordance with the classification.Embodiments of the provider-side network node 150 can include any othersuitable components, such as edge servers, traffic shapers, networkaccelerators, data classifiers, and/or any other suitable components.Though only one provider-side network node 150 is shown as coupled withall the communications networks 132, other embodiments are implementedwith other architectures. For example, some or all of the communicationsnetworks 132 can terminate at respective provider sides in respectiveprovider-side network nodes 150 (e.g., gateways, head-ends, mobileswitching centers, etc.), and those provider-side network nodes 150 canbe in communication with another provider-side network node 150 (e.g., acore node, or the like) that performs forward-link routing functionalitydescribed herein.

Routing traffic through a hybrid communications network 130 involvesdetermining, for each suitable unit of traffic (e.g., each traffic flow,each established logical connection, each deterministically sized chunkof data, each packet, etc.), over which of the communications networks132 to route the traffic. In the forward-link direction, traffictypically originates at one of the content hosts 172 and is destined forone of the CPEs 102. The traffic can be intercepted by the provider-sidenetwork node 150, and the provider-side network node 150 can determinean appropriate routing or forwarding decision, for example, byclassifying the content of the traffic. As an example, in a particularhousehold, one member of the household is streaming a movie whileanother is surfing the internet. The provider-side network node 150 maydetermine to deliver the streaming movie over a first of thecommunications networks 132 a that is a satellite network (e.g., becausethe higher throughput will yield a high-quality stream of the movie, andthe higher latency will not have an appreciable impact on the viewingexperience) and to deliver the Internet surfing traffic over a second ofthe communications networks 132 b that is a DSL network (e.g., becausereduced latency will likely benefit the surfing experience, while thereduction in throughput will likely not have an appreciable impact onthe surfing experience).

The data classification and other aspects of the routing determinationscan be highly computationally intensive. For example, the classifyingcan involve deep packet inspection, statistical processing, etc. Still,typical provider-side network nodes 150 can be implemented withsufficient computational resources to perform such determinations forforward-link traffic, even substantially in real time and for largenumbers of traffic flows. However, it is typically desirable for theuser terminals 110 to be implemented at relatively low cost and withrelatively low complexity. For example, while the provider-side networknode 150 can be implemented in a large and expensive computationalenvironment, it is typically desirable for each user terminal 110 to beimplemented as a small, inexpensive, reliable, simple device that can beinstalled in each user's premises. Accordingly, user terminals 110typically may not have sufficient processing capability to make suchdeterminations for return-link traffic.

Accordingly, embodiments described herein include novel systems andmethods for providing return-link routing in a user terminal 110 incommunication with a hybrid communications network 130. As illustrated,each user terminal 110 includes a user terminal routing system (UTRS)120 coupled between the hybrid network interface 125 and the localnetwork interface 127. The UTRS 120 includes a routing module 114 and arouting table 112. As described herein, rather than makingcomputationally intensive routing determinations, the routing module 114can make routing determinations according to mappings populated anddynamically updated in the routing table 112 according to receivedforward-link communications. For example, each mapping associates arouting table entry with one of the communications networks 132, suchthat, when return-link traffic is received by the routing module 114(from a CPE 102), the routing module 114 can find a mapping in therouting table 112 that has a corresponding routing table entry and canroute the return-link traffic, accordingly. Each routing table entry canbe uniquely identified at least according to a forward-link contentsource (FLCS) identifier. For example, the FLCS identifier can be anInternet protocol (IP) address that was the source IP address ofpreviously received forward-link traffic and may be the destination IPaddress of subsequent return-link traffic. As described herein, the FLCSidentifier can be obtained or derived from a routing tuple (e.g., a2-tuple, a 5-tuple, etc.), a control message, a domain name server (DNS)lookup or reverse lookup, or in any other suitable manner. The routingtable 112 can be implemented as a lookup table, or the like, which canbe queried very quickly and with very low computational intensity.

FIGS. 2A-2C show a first set of examples in which return-link routingdeterminations are made by a user terminal 110 in a hybridcommunications environment 200. In the illustrated set of examples,return-link routing determinations are made in accordance with receiptof forward-link communications. Turning first to FIG. 2A, a thick dashedarrow indicates a forward-link traffic flow path originating at one ofthe host computers 172 in the content networks 175 and terminating inone of the CPEs 102 of a local user network 105 associated with a userterminal 110. The flow is received (e.g., intercepted) by aprovider-side network node 150. A provider-side routing module 160 inthe provider-side network node 150 can classify the traffic and/or makeany determinations to support a decision as to over which of thecommunications networks 132 to route the traffic. The traffic can beoutput to the hybrid communications network 130 via an appropriateinterface (e.g., port 142) of the provider-side hybrid network interface145. In the illustrated case, the determination is to route the trafficto a first communications network 132 a via a first interface port 142 a(e.g., and a level 3 router, not shown), where the first communicationsnetwork 132 a is a satellite network.

The traffic is received from the first communications network 132 a viaa first interface port 122 of the hybrid network interface 125 of theuser terminal 110 and is passed to the routing module 114 of the UTRS120. The forward-link traffic can be passed from the UTRS 120 to theappropriate destination CPE 102 via the local network interface 127.Additionally, as described more fully below, the routing module 114 canupdate (and/or determine whether to update) the routing table 112mappings based on the received traffic. In the illustrated case, therouting module 114 can generate or update a mapping in the routing table112 based on the source IP address of the traffic and the network overwhich the traffic was received (i.e., the first communications network132 a). In some implementations, the forward-link traffic packetsinclude a tuple that includes at least a source IP address. For example,the tuple can be a 2-tuple that indicates a source IP address and asource port; or the tuple can be a 5-tuple that indicates a source IPaddress, a source port, a destination IP address, a destination port,and a communications protocol. The routing module 114 can store at leastthe source IP address as a FLCS identifier of a routing table entry. TheFLCS identifier can be the routing table entry, or the routing tableentry can include the FLCS and additional information. For example, someimplementations can invert the received 5-tuple, store the inverted5-tuple as the routing table entry (i.e., so that the source port and IPaddress of the 5-tuple is stored as the destination port and IP address)in the routing table entry), and map the routing table entry to thereceiving communications network 132. The additional information can beused in certain embodiments. For example, some embodiments can havedifferent return-link mappings for traffic from different CPEs 102,having different communications protocols, etc., even when destined fora same content host 172.

Turning to FIG. 2B, subsequent to updating the routing table 112according to the received forward-link traffic in FIG. 2A, return-linktraffic is received by the UTRS 120 from a CPE 102 of the local usernetwork 105. When the return-link traffic is received, the routingmodule 114 can determine (e.g., parse) a destination identifier for thereturn-link traffic and can identify one of the mappings in the routingtable 112 that corresponds with the destination identifier. For example,the return-link traffic can indicate a destination IP address thatmatches the FLCS identifier of one of the routing table entries. Theidentified mapping in the routing table 112 maps the FLCS identifier toone of the communications networks 132. In the illustrated case, thereturn-link traffic is destined for the same host computer 172 fromwhich the forward-link traffic was received over the satellite network(first communications network 132 a) in FIG. 2A. The mapping updated inFIG. 2A associates the FLCS identifier for that host computer 172 withthe first communications network 132 a. Accordingly, as illustrated, theUTRS 120 can determine (according to the routing table 112) to route thereceived return-link traffic to the destination host 172 a over thefirst communications network 132 a (e.g., via interface port 142 a andthe provider-side routing module 160).

In some cases, traffic associated with a particular host computer 172can be routed differently in the forward-link and return-linkdirections. FIG. 2C illustrates such a case, in which return-linktraffic, though destined for the first host computer 172 a (previouslymapped to the first communications network 172 a in the routing table112 in FIG. 2A), is routed through a second communications network 172 bof the hybrid communications network 130. Such a case can arise in anumber of different contexts. In one such context, the each routingtable of the routing table 112 is uniquely identified by more than justthe destination identifier. For example, the routing table 112 caninclude multiple routing table entries having the same destinationidentifier, but having different other parameters (e.g., differentprotocols, etc.). As an example of such a context, the forward-linktraffic received from the host computer 172 a in FIG. 2A is part of atraffic flow for a streaming movie, while the return-link traffic sentin FIG. 2C is a playback navigation message (e.g., ‘pause’) being sentfrom the CPE 102 a back to the host computer 172 a. In another suchcontext, the routing module 114 and/or routing table 112 includescertain routing directives that route certain traffic according tocertain rules, regardless of whether there is a conflicting mapping inthe routing table 112. For example, the routing module 114 can include arule (or the routing table 112 can have a hierarchically dominantmapping) that always routes return-link traffic from a particular CPE102 (e.g., from a particular private return-link source IP address) overthe second communications network 132 b. In yet another such context,other network considerations can take precedence over the routing table112. For example, detected network congestion on the firstcommunications network 132 a can trigger diversion of traffic (e.g., oflarge file uploads) from the first communications network 132 a to thesecond communications network 132 b, regardless of any mappings to thecontrary. In still another context, mappings in the routing module 114can have associated validity windows, or other types of hysteresis, orthe like. For example, some or all mappings may be changed only after apredetermined threshold number of change events occurs (e.g., only afterthree traffic flows in a row are received from a particular hostcomputer 172 over the same one of the communications network 132), orsome or all mappings may only be valid over a particular window (e.g.,the mapping(s) automatically reset to a default mapping after someduration of time has elapsed since a last event confirming the mapping,after a particular logical connection session ends, etc.).

FIG. 3 shows a second example in which return-link routingdeterminations are made by a user terminal 110 in a hybridcommunications environment 300. In the illustrated example, return-linkrouting determinations are made in accordance with receipt of controlmessages via forward-link communications. A thick dashed arrow indicatesa forward-link control message flow path originating at theprovider-side routing module 160 of the provider-side network node 150.The control messages are output to the hybrid communications network 130via an appropriate interface (e.g., port 142) of the provider-sidehybrid network interface 145. While the illustrated case shows thecontrol message being routed over one particular communications network132, other implementations can send the control messages over any one ormore of the communications networks 132. The control messages arereceived from the hybrid communications network 130 (e.g., from thefirst communications network 132 a) via the hybrid network interface 125of the user terminal 110 (e.g., via the first interface port 122 a) andis passed to the routing module 114 of the UTRS 120. In this case, thecontrol messages are not passed to a CPE 102, as they are tailored to beused directly by the UTRS 120 to generate and/or update mappings. Therouting module 114 can obtain (e.g., parse, derive, etc.) routing tableupdates from the received control messages and can update the routingtable 112, accordingly. For example, the control messages can include alist of routing table entries (e.g., FLCS identifiers, 5-tuples, etc.)and associated communications networks 132, from which mappings can begenerated. Some embodiments use a combination of techniques to populateand/or dynamically update the routing table 112, for example, using bothcontrol messages as in FIG. 3 and forward-link traffic data as in FIG.2A.

FIG. 4 shows a block diagram of a user terminal environment 400,including an illustrative user terminal 110 in communication with alocal user network 105 and a hybrid communications network 130,according to various embodiments. As illustrated, forward-link traffic402 is received from the hybrid communications network 130 and directedto an appropriate CPE in the local user network 105, and return-linktraffic 452 is received from a CPE of the local user network 105 androuted (e.g., forwarded, routed, etc.) to an appropriate communicationsnetwork of the hybrid communications network 130. The user terminal 110can include a hybrid network interface 125 and a user terminal routingsystem (UTRS) 120, having a routing table 112 and a routing moduleimplemented as a routing state machine 414. In some embodiments, therouting table 112 is implemented as a lookup table. In otherimplementations, the routing table 112 is implemented as any suitabletype of fast-access data store.

Embodiments of the hybrid network interface 125 can include physicaland/or logical network interfaces (e.g., ports 122) that can be adaptedto the particular component networks of the hybrid communicationsnetwork 130. The hybrid network interface 125 can also include a router470 for layer 3 routing (e.g., over a primary one of the componentnetworks, such as a satellite network) and a forwarder 475 for layer 2forwarding (e.g., implementing a layer 2 tunnel endpoint). Someembodiments of the hybrid network interface 125 can include additionalnetwork interface components, such as a network address translator (NAT)460. For example, the NAT 460 can translate between private IP addressesof the CPEs of the local user network 105 and a public address of theuser terminal 110 as seen by the hybrid communications network 130.

As illustrated, embodiments of the UTRS 120 include (e.g., are coupledwith, have integrated within, etc.) a local network interface 127operable to couple with a local user network 105. The UTRS 120 alsoincludes a hybrid network interface 125 that has multiple networkinterfaces 122, each operable to couple with a respective one of themultiple communications networks 132 of the hybrid communicationsnetwork 130. The UTRS 120 also includes a routing table 112 havingstored thereon multiple mappings populated according to forward-linkcommunications (e.g., 402, 412) received via at least one of thecommunications networks 132. Each mapping associates a respective one ofa number of routing table entries with one of the communicationsnetworks 132, and each routing table entry identifies at least aforward-link content source (FLCS) identifier (e.g., a host computer IPaddress).

The UTRS 120 also includes a routing module 114, which can beimplemented as a routing state machine 414, as shown. The routing statemachine 414 can be implemented in any suitable manner. In someimplementations, the routing state machine 414 is a hardware statemachine that performs various functions using circuits, such asprogrammable circuits, processors, etc. In other implementations, somefunctions are implemented in hardware, software, firmware, or anycombination thereof. If implemented in software, the functions can bestored as one or more instructions on a non-transitory computer-readablemedium. A storage medium can be any available tangible medium that canbe accessed by a computer. By way of example, and not limitation, suchcomputer-readable media can include RAM, ROM, EEPROM, CD-ROM, or otheroptical disk storage, magnetic disk storage, or other magnetic storagedevices, or any other tangible medium that can be used to carry or storedesired program code in the form of instructions or data structures andthat can be accessed by a computer.

Embodiments of the routing state machine 414 are coupled between thelocal network interface 127 and the hybrid network interface 125, andthe routing state machine 414 includes a routing state output 442computed according to the routing table 112 in response to receivingreturn-link data 452 via the local network interface 127. The receivedreturn-link data 452 indicates a destination node corresponding to theFLCS identifier of an identified one of the mappings, and the routingstate output 442 directs routing of the received return-link data 452over a selected one of the communications networks 132 via the hybridnetwork interface 125 in accordance with the identified one of themappings.

Some embodiments of the UTRS 120 include some or all of a mappinggenerator 430 and a return-link router 440. In some embodiments, therouting table 112 is updated according to received forward-link traffic402. As described herein, embodiments can populate and/or update routingtable 112 mappings in various ways, including according to receivedforward-link traffic flows 402 and/or control messages 412. For addedclarity, FIG. 4 shows both types of forward-link communications beingreceived by the user terminal 110 (and by the UTRS 120). Further, themapping generator 430 is illustrated as having both a network-basedupdater 410 and a control-based updater 420 for updating mappings inresponse to forward-link traffic 402 and control messages 412,respectively. Some implementations of the mapping generator 430 includeonly one of the network-based updater 410 or the control-based updater420.

In some embodiments, the forward-link traffic 402 is received by thehybrid network interface 125 from one of the communications networks 132and passed to the network-based updater 410 of the mapping generator430. The network-based updater 410 can obtain (e.g., parse, derive,etc.) a routing profile for the received forward-link traffic 402 thatincludes at least a FLCS identifier (e.g., as the source IP address). Insome cases, the routing profile can include an identifier of thecommunications network 132 over which the forward-link traffic 402 wasreceived, the source port, the destination IP address, the destinationport, the routing protocol, and/or other characteristics of theforward-link traffic 402. The network-based updater 410 can use theobtained routing profile to generate (e.g., create, update, etc.) amapping in the routing table 112. For example, the FLCS identifier canbe stored as a routing table entry in mapped association with thecommunications network 132 over which the traffic was received, or a5-tuple of the received forward-link traffic 402 can be inverted andstored as the routing table entry and mapped to an appropriate one ofthe communications networks 132. The updated mapping can be populated bythe mapping generator 430 to the routing table 112.

Similarly, control messages 412 can be received as forward-linkcommunications by the hybrid network interface 125 from one or more ofthe communications networks 132. The control messages 412 can be passedto the control-based updater 420 of the mapping generator 430, and thecontrol-based updater 420 can obtain (e.g., parse, derive, etc.) one ormore mapping updates therefrom. For example, the control messages 412can indicate a list of mappings between each of a number of FLCSidentifiers (and/or other routing profile information) and respectiveones of the communications networks 132 over which to route (e.g.,route, forward, etc.) return-link data destined for a host computercorresponding to the FLCS. The updated mappings can be populated by themapping generator 430 to the routing table 112.

In some embodiments, the routing table 112 is at least partiallypre-populated and/or automatically populated with information notarising from forward-link communications. In such cases, the routingtable 112 is still dynamically updated and/or further populated fromforward-link communications (e.g., from forward-link traffic 402 and/orcontrol messages 412). In some such embodiments, the routing table 112is preloaded with default mappings (e.g., prior to deployment to acustomer premises, as part of initializing the device at the customer'spremises, etc.). Some such embodiments include a domain name server(DNS) lookup module 437. For example, the routing table 112 can bepre-populated with default mappings between host names (e.g., contentdomains) and particular ones of the communications networks 132 overwhich to route return-link traffic to those hosts. With the UT 110(e.g., and the UTRS 120) coupled to the hybrid communications network130, the DNS lookup module 437 can perform DNS lookups to resolve themapped host names into IP addresses for use as FLCS identifiers inrouting table entries. In some implementations, the DNS lookup module437 can periodically (e.g., according to a schedule, whenevercommunications indicate that host name, and/or at any other suitabletime) re-resolve some or all of the host names to ensure that theassociations remain fresh. Alternatively, the resolved host IP addressesare only used for the default mappings, and some or all of thosemappings are dynamically updated in accordance with receivedforward-link communications, as described herein. In someimplementations, associations between the host names and the resolvedhost IP addresses can be stored for further use, for example, asdescribed below. For example, a control message 412 can indicate aparticular mapping update for all IP addresses associated with aparticular group of related hosts (e.g., where one content host usesmultiple IP addresses as mirror sites, as content distribution networks(CDNs), etc.; where a particular group of host names is associated witha same class of traffic (e.g., video streaming); etc.); and the storedassociations can be used to quickly update the mappings for multiplerouting table entries in accordance with their association with theindicated hosts.

Some embodiments of the mapping generator 430 include, or are incommunication with, a validator 435 that is coupled with a storedrulebase 450. Embodiments of the validator 435 can determine whether andwhen to permit the mapping generator 430 to update mappings in therouting table 112 according to rules in the rulebase 450. In someembodiments, some or all of the rules in the rulebase 450 are hard-codedprior to deployment of the user terminal 110. In other embodiments, someor all of the rules of the rulebase 450 are hardware or softwareprogrammable according to control messages 412 received via the hybridnetwork interface 125, by local user commands received via the localnetwork interface 127, and/or in any other suitable manner. In someimplementations, the rulebase 450 defines a validity window for some orall mappings in the routing table 112. For example, a particular mappingcannot be updated more than some number of times within a particulartimeframe (e.g., more than once per hour), cannot be updated within acertain amount of time since its last update, etc. In otherimplementations, the rulebase 450 defines an update threshold for someor all of the mappings. For example, a particular mapping may only beupdated after a certain number of flows from a particular host isreceived over a same network that is different from what is currentlymapped. In other implementations, the rulebase 450 defines other typesof update conditions. For example, some hybrid communications networks130 can be defined to have a hierarchy (e.g., a primary one of thecommunications networks 132, where all the other communications networks132 are secondary networks; each of the communications networks 132 isin a priority order; etc.). In such a case, particular rules can takeeffect when a mapping is being changed from a primary network to asecondary network, from a secondary network to a primary network, etc.For example, the rulebase 450 can be designed so that it is easier toupdate mappings from primary networks to secondary networks than fromsecondary networks to primary networks (e.g., tending toward offloadingtraffic from the primary network).

As illustrated, in addition to using the received forward-link traffic402 for updating mappings, the forward-link traffic 402 can be forwardedto the appropriate destination CPE in the local user network 105. Thoughshown as being forwarded from the network-based updater 410, theforward-link traffic 402 can be forwarded in any suitable manner, forexample, directly from the hybrid network interface 125. The CPE(s) ofthe local user network 105 can also originate return-link traffic flows452 destined for some destination host over the hybrid communicationsnetwork 130. The return-link traffic flows 452 are received by thereturn-link router 440 of the UT 110 via the local network interface127, so that the return-link router 440 can determine over which of thecommunications networks 132 to route the return-link traffic flows 452.As described herein, embodiments can rapidly make such determinationswith little computational intensity by relying on the mappings stored inthe routing table 112. For example, the return-link router 440 obtains(e.g., parses, derives, etc.) a destination identifier (e.g., adestination IP address) from the return-link traffic flow 452 andidentifies a routing table entry in the routing table 112 thatcorresponds to (e.g., matches) the obtained destination identifier. Forexample, the return-link router 440 performs a lookup on the routingtable 112. The identified mapping can indicate over which of thecommunications networks 132 to route the return-link traffic 452.

Various embodiments can include additional considerations that canimpact the routing determination. In some such embodiments, thereturn-link router 440 is coupled with, or includes, the validator 435(e.g., or there is a separate validator 435 and rulebase 450 for thereturn-link router 440). As described above, in some implementations,the rulebase 450 defines a validity window for some or all mappings inthe routing table 112. In an example return-link routing context, aparticular mapping may only be valid for some predetermined about oftime since it was last updated, after which it can revert to a prior(e.g., default) mapping. Alternatively, a particular mapping is onlyvalid at certain times of day, when certain networks have presentlyavailable capacity, etc. In such cases, the return-link router 440 maymake routing determinations based on rules of the rulebase 450, even ifthe rules conflict with one or more mappings in the routing table 112.

In other such embodiments, the return-link router 440 is coupled with,or includes, the DNS lookup module 437 (e.g., or there is a separate DNSlookup module 437 for the return-link router 440). As described above,associations between the host names and the resolved host IP addressescan be stored for further use. For example, the return-link router 440can use the stored associations to quickly resolve host names todestination IP addresses in support of routing return-link traffic. Inother implementations, the DNS lookup module 437 can be used to performa reverse DNS lookup, by which to obtain a host name from an IP address.For example, the mappings can include particular mappings (e.g., orrules can be included in the rulebase 450) for routing trafficassociated with certain hosts via certain communications networks 132,even where no other corresponding routing table entry is in the routingtable 112 (e.g., where the return-link traffic indicates a differentdestination IP address for a content host than what is mapped in therouting table 112). In such a case, it can be desirable to perform thereverse DNS lookup to determine, for example, whether a correspondinghost has previously been mapped in the routing table 112, even if theindicated destination IP address has not.

In some of these and other embodiments, the DNS lookups and/or reverseDNS lookups of the DNS lookup module 437 may take too much time toperform as part of a real-time return-link routing determination.Accordingly, some embodiments of the DNS lookup module 437 can performDNS lookups and/or reverse DNS lookups as background tasks (e.g., inparallel with the return-link router 440 making routing determinations).For example, when a return-link traffic flow 452 is received by thereturn-link router 440, the return-link router 440 can proceed withmaking real-time routing determinations according to mappings availablein the routing table 112 and/or according to the rulebase 450 (e.g.,default mappings, etc.). Meanwhile, the return-link router 440 can alsotrigger the DNS lookup module 437 to perform DNS lookups and/or reverseDNS lookups, which may result in an update to, or addition of, one ormore mappings. The updated or new mappings can then be used by thereturn-link router 440 to route subsequent packets of the samereturn-link traffic flow 452 and/or subsequent flows.

Having made a routing determination, the return-link router 440 canoutput the return-link traffic flows 452 and the routing determinationas the routing state output 442. The hybrid network interface 125 canuse the routing state output 442 to route the return-link traffic flows452 over the hybrid communications network 130. For example, the hybridnetwork interface 125 can route the return-link traffic flows 452 over aprimary one of the component networks 132 (e.g., a satellite network) asa layer 3 routing using the router 470, can route the return-linktraffic flows 452 over a layer 2 tunnel via a secondary one of thecommunications networks 132 using the forwarder 475, etc. In someembodiments, additional functionality is performed by the hybrid networkinterface 125 as part of routing the return-link traffic flows 452 overthe hybrid communications network 130. For example, the NAT 460 cantranslate the private IP address of the source CPE into a public IPaddress of the UT 110. Further, implementations can packetize the data,modulate the data, and/or otherwise prepare the return-link trafficflows 452 for communication over the selected communications networks132.

FIG. 5 shows a flow diagram of an illustrative method 500 forreturn-link routing by a user terminal in a hybrid networkingenvironment, according to various embodiments. Embodiments of the method500 can be performed using the systems described with reference to FIGS.1-4, or any other suitable systems. Embodiments of the method 500 beginat stage 504 by receiving return-link data at a user terminal routingsystem from consumer premises equipment (CPE), the return-link dataindicating an associated destination node for the return-link data. Asdescribed herein, the user terminal routing system (UTRS) iscommunicatively coupled with multiple networks and has a routing tablepopulated according to forward-link communications received by the userterminal routing system from at least one of the networks. For example,one of the networks is a satellite network, and the routing table ispopulated according to forward-link communications received by the UTRSfrom a provider-side core node (e.g., or gateway) of the satellitenetwork. In various implementations, the core node is communicativelycoupled with one, multiple, or all of the networks of the hybridnetwork. The routing table can be a lookup table, or other suitable datastore having, stored thereon, multiple mappings, each between arespective routing table entry and one of the networks. Each routingtable entry identifies at least a forward-link content source (FLCS)identifier.

At stage 508, embodiments identify one of the mappings in the routingtable as having the routing table entry that corresponds to thedestination node associated with the return-link data. For example, therouting table entries can include any suitable FLCS identifier, such asa return-link destination IP address. In some embodiments, each routingtable entry includes a five-tuple that identifies a source IP address, asource port, a destination IP address, a destination port, and a datacommunication protocol. The return-link data can include a return-linkrouting tuple that indicates the associated destination node for thereturn-link data. The return-link routing tuple can further indicate adestination Internet protocol (IP) address, and a destination port.

At stage 512, embodiments route the return-link data over one of thenetworks according to the identified one of the mappings. In someembodiments, the routing at stage 512 is directly in accordance with thestored mappings. For example, forward-link data is received from aparticular content host over a particular one of the networks, andreturn-link data sent to that content host is sent over the sameparticular one of the networks. In other embodiments, the routing canaccount for other factors. As illustrated, some embodiments determine atstage 516 whether the mapping identified in stage 508 is valid as is.For example, the routing is directly according to the mapping in stage512 only if the mapping is determined to be valid at stage 516, and therouting can be adjusted if the mapping is determined not to be valid atstage 516. For example, the routing at stage 512 can be adjusted instage 520 according to a routing rule-base that defines a set of routingcriteria and an alternate network of the plurality of networks, suchthat, in accordance with whether the set of routing criteria is met, therouting of the return-link data is either over the one of the networksmapped in the routing table to the destination node of the return-linkdata or over the alternate network.

Similar types of validation, enforcement, adjustment, etc. regarding theroutings can be implemented in different ways according to differentembodiments. In some embodiments, forward-link data is received at theuser terminal via one of the plurality of networks, the forward-linkdata indicating a source node for the forward-link data. A correspondingone of the mappings of the routing table can be identified ascorresponding to the indicated source node, and a determination can bemade as to whether the corresponding mapping is presently enforcedaccording to a validity window associated with the identified one of themappings. In such embodiments, the corresponding mapping may be updatedaccording to the received forward-link data only when the correspondingmapping is not presently enforced. In other such embodiments,forward-link data packets can be received at the user terminal via atleast one of the plurality of networks, and each forward-link datapacket can indicate a respective source node for the forward-linkpacket. The method 500 can wait to detect receipt of at least athreshold number of the forward-link data packets that all have a samerespective source node and are all received over a first network of theplurality of networks; and only after such detecting, can update therouting table with an updated mapping in response to the detecting. Insuch embodiments, the updating includes mapping the first network to arouting table entry corresponding to the same respective source node. Inyet other such embodiments, the method 500 can determine whether theidentified one of the mappings is presently valid according to avalidity window associated with the identified one of the mappings, andthe routing at stage 512 can be performed according to the identifiedone of the mappings only when the identified one of the mappings ispresently valid. In still other such embodiments, the method 500 canreceive forward-link data at the user terminal via a first network ofthe plurality of networks (the forward-link data indicating a sourcenode for the forward-link data); a corresponding one of the mappings ofthe routing table can be identified as corresponding to the indicatedsource node; a determination can be made that the corresponding mappingpresently directs routing over a second network of the plurality ofnetworks; and the corresponding mapping can be updated to direct routingover the first network only when the second network is a primary networkof the plurality of networks, and the first network is not the primarynetwork of the plurality of networks.

Some embodiments of the method 500 begin by populating and/or updatingsome or all of the routing table mappings prior to the receiving atstage 504. For example, at stage 501, embodiments can receiveforward-link data at the user terminal via a first of the networks priorto receiving the return-link data at stage 504. The forward-link datacan indicate a source node for the forward-link data, and the routingtable can be updated with an updated mapping according to the receivedforward-link data. In such embodiments, the identifying at stage 508 caninclude determining that the destination node for the return-link datacorresponds to the source node for the forward-link data, such that theidentified one of the mappings is the updated mapping; and the routingat stage 512 can include routing the return-link data over the firstnetwork according to the updated mapping. In some such embodiments, theupdating at stage 501 includes mapping the first network to a routingtable entry for the source node, and the routing at stage 512 includesrouting the return-link data over the first network according to theupdated mapping. Other embodiments of the method 500 can begin at stage502 by receiving a control message at the user terminal via one of thenetworks (e.g., the control message indicates at least one routing tableupdate) and updating the routing table according to the at least onerouting table update. Still other embodiments of the method 500 begin atstage 503 by pre-populating some or all of the routing table, forexample, with default mappings. For example, each of at least a portionof the preloaded mappings can be preloaded by: selecting one of amultiple pre-stored associations between a corresponding content hostand a corresponding one of the plurality of networks; performing adomain name server (DNS) lookup to determine a destination IP addressassociated with the corresponding content host; and generating thepreloaded mapping to associate the corresponding one of the plurality ofnetworks with a routing table entry comprising the destination IPaddress. Similarly, in some embodiments, at least one of the routingtable entries can indicate a return-link destination IP address, and atleast one of the mappings can be generated by: determining a contenthost corresponding to the return-link destination IP address indicatedby the at least one routing table entry; identifying a pre-storedassociation between the content host and a routing network of theplurality of networks; and generating the at least one mapping toassociate the routing table entry with the identified routing network.For example, the content host can be determined by performing a reverseDNS lookup (e.g., by the UTRS as a background task concurrently with theidentifying at stage 508 and/or the routing at stage 512).

The methods disclosed herein include one or more actions for achievingthe described method. The method and/or actions can be interchanged withone another without departing from the scope of the claims. In otherwords, unless a specific order of actions is specified, the order and/oruse of specific actions can be modified without departing from the scopeof the claims.

A computer program product can perform certain operations presentedherein. For example, such a computer program product can be a computerreadable tangible medium having instructions tangibly stored (and/orencoded) thereon, the instructions being executable by one or moreprocessors to perform the operations described herein. The computerprogram product can include packaging material. Software or instructionscan also be transmitted over a transmission medium. For example,software can be transmitted from a website, server, or other remotesource using a transmission medium such as a coaxial cable, fiber opticcable, twisted pair, digital subscriber line (DSL), or wirelesstechnology such as infrared, radio, or microwave.

Further, modules and/or other appropriate means for performing themethods and techniques described herein can be downloaded and/orotherwise obtained by suitable terminals and/or coupled to servers, orthe like, to facilitate the transfer of means for performing the methodsdescribed herein. Alternatively, various methods described herein can beprovided via storage means (e.g., RAM, ROM, a physical storage mediumsuch as a CD or floppy disk, etc.), such that a user terminal and/orbase station can obtain the various methods upon coupling or providingthe storage means to the device. Moreover, any other suitable techniquefor providing the methods and techniques described herein to a devicecan be utilized. Features implementing functions can also be physicallylocated at various positions, including being distributed such thatportions of functions are implemented at different physical locations.

In describing the present invention, the following terminology will beused: The singular forms “a,” “an,” and “the” include plural referentsunless the context clearly dictates otherwise. Thus, for example,reference to an item includes reference to one or more items. The term“ones” refers to one, two, or more, and generally applies to theselection of some or all of a quantity. The term “plurality” refers totwo or more of an item. The term “about” means quantities, dimensions,sizes, formulations, parameters, shapes and other characteristics neednot be exact, but can be approximated and/or larger or smaller, asdesired, reflecting acceptable tolerances, conversion factors, roundingoff, measurement error and the like and other factors known to those ofskill in the art. The term “substantially” means that the recitedcharacteristic, parameter, or value need not be achieved exactly, butthat deviations or variations including, for example, tolerances,measurement error, measurement accuracy limitations and other factorsknown to those of skill in the art, can occur in amounts that do notpreclude the effect the characteristic was intended to provide.Numerical data can be expressed or presented herein in a range format.It is to be understood that such a range format is used merely forconvenience and brevity and thus should be interpreted flexibly toinclude not only the numerical values explicitly recited as the limitsof the range, but also interpreted to include all of the individualnumerical values or sub-ranges encompassed within that range as if eachnumerical value and sub-range is explicitly recited. As an illustration,a numerical range of “about 1 to 5” should be interpreted to include notonly the explicitly recited values of about 1 to about 5, but alsoinclude individual values and sub-ranges within the indicated range.Thus, included in this numerical range are individual values such as 2,3 and 4 and sub-ranges such as 1-3, 2-4 and 3-5, etc. This sameprinciple applies to ranges reciting only one numerical value (e.g.,“greater than about 1”) and should apply regardless of the breadth ofthe range or the characteristics being described. A plurality of itemscan be presented in a common list for convenience. However, these listsshould be construed as though each member of the list is individuallyidentified as a separate and unique member. Thus, no individual memberof such list should be construed as a de facto equivalent of any othermember of the same list solely based on their presentation in a commongroup without indications to the contrary. Furthermore, where the terms“and” and “or” are used in conjunction with a list of items, they are tobe interpreted broadly, in that any one or more of the listed items canbe used alone or in combination with other listed items. The term“alternatively” refers to selection of one of two or more alternatives,and is not intended to limit the selection to only those listedalternatives or to only one of the listed alternatives at a time, unlessthe context clearly indicates otherwise. The term “coupled” as usedherein does not require that the components be directly connected toeach other. Instead, the term is intended to also include configurationswith indirect connections where one or more other components can beincluded between coupled components. For example, such other componentscan include amplifiers, attenuators, isolators, directional couplers,redundancy switches, and the like. Also, as used herein, including inthe claims, “or” as used in a list of items prefaced by “at least oneof” indicates a disjunctive list such that, for example, a list of “atleast one of A, B, or C” means A or B or C or AB or AC or BC or ABC(i.e., A and B and C). Further, the term “exemplary” does not mean thatthe described example is preferred or better than other examples. Asused herein, a “set” of elements is intended to mean “one or more” ofthose elements, except where the set is explicitly required to have morethan one or explicitly permitted to be a null set.

Various changes, substitutions, and alterations to the techniquesdescribed herein can be made without departing from the technology ofthe teachings as defined by the appended claims. Moreover, the scope ofthe disclosure and claims is not limited to the particular aspects ofthe process, machine, manufacture, composition of matter, means,methods, and actions described above. Processes, machines, manufacture,compositions of matter, means, methods, or actions, presently existingor later to be developed, that perform substantially the same functionor achieve substantially the same result as the corresponding aspectsdescribed herein can be utilized. Accordingly, the appended claimsinclude within their scope such processes, machines, manufacture,compositions of matter, means, methods, or actions.

1.-35. (canceled)
 36. A method for routing signals in a hybrid network,the method comprising: receiving return-link data at a user terminalrouting system from consumer premises equipment, the return-link dataindicating an associated destination node for the return-link data; theuser terminal routing system communicatively coupled with a plurality ofnetworks having different network characteristics and comprising arouting table populated, prior to receipt of the return-link data at theuser terminal routing system, with a plurality of mappings, each mappingassociating a destination node associated with the return-link data andone of the plurality of networks; identifying one of the mappings in therouting table as corresponding to the destination node associated withthe return-link data; and routing the return-link data over one of theplurality of networks according to the identified one of the mappings.37. The method of claim 0, further comprising: receiving forward-linkdata at the user terminal via a first network of the plurality ofnetworks prior to receiving the return-link data, the forward-link dataindicating a source node for the forward-link data; and updating therouting table with an updated mapping according to the receivedforward-link data, wherein the identifying comprises determining thatthe destination node for the return-link data corresponds to the sourcenode for the forward-link data, such that the identified one of themappings is the updated mapping, and the routing comprises routing thereturn-link data over the first network according to the updatedmapping.
 38. The method of claim 0, wherein: the updating comprisesmapping the first network to a routing table entry for the source node;and the routing comprises routing the return-link data over the firstnetwork according to the updated mapping.
 39. The method of claim 0,further comprising: receiving a control message at the user terminal viaone of the plurality of networks, the control message indicating atleast one routing table update; and updating the routing table accordingto the at least one routing table update.
 40. The method of claim 0,wherein each routing table entry comprises a five-tuple that identifiesa source Internet protocol (IP) address, a source port, a destination IPaddress, a destination port, and a data communication protocol.
 41. Themethod of claim 0, wherein: the return-link data comprises a return-linkrouting tuple that indicates the associated destination node for thereturn-link data.
 42. The method of claim 0, wherein the return-linkrouting tuple further indicates a destination Internet protocol (IP)address, and a destination port.
 43. The method of claim 0, wherein: oneof the plurality of networks is a satellite network; and the routingtable is populated according to forward-link communications received bythe user terminal routing system from a provider-side core node of thesatellite network.
 44. The method of claim 0, wherein the core node iscommunicatively coupled with multiple of the plurality of networks. 45.The method of claim 0, further comprising: receiving a plurality offorward-link data packets at the user terminal via at least one of theplurality of networks, each forward-link data packet indicating arespective source node for the forward-link packet; detecting receipt ofat least a threshold number of the forward-link data packets that allhave a same respective source node and are all received over a firstnetwork of the plurality of networks; and updating the routing tablewith an updated mapping in response to the detecting, the updatingcomprising mapping the first network to a routing table entrycorresponding to the same respective source node.
 46. The method ofclaim 0, wherein: routing the return-link data according to theidentified one of the mappings comprises routing according to a routingrule-base that defines a set of routing criteria and an alternatenetwork of the plurality of networks, such that, in accordance withwhether the set of routing criteria is met, the routing of thereturn-link data is either over the one of the plurality of networksmapped in the routing table to the destination node of the return-linkdata or over the alternate network.
 47. The method of claim 0, furthercomprising: determining, by the user terminal routing system, whetherthe identified one of the mappings is presently valid according to avalidity window associated with the identified one of the mappings; androuting the return-link data according to the identified one of themappings only when the identified one of the mappings is presentlyvalid.
 48. The method of claim 0, further comprising: receivingforward-link data at the user terminal via a first network of theplurality of networks, the forward-link data indicating a source nodefor the forward-link data; identifying a corresponding one of themappings of the routing table as corresponding to the indicated sourcenode; determining, by the user terminal routing system, that thecorresponding mapping presently directs routing over a second network ofthe plurality of networks; and updating the corresponding mapping todirect routing over the first network only when the second network is aprimary network of the plurality of networks, and the first network isnot the primary network of the plurality of networks.
 49. The method ofclaim 0, further comprising: receiving forward-link data at the userterminal via one of the plurality of networks, the forward-link dataindicating a source node for the forward-link data; identifying acorresponding one of the mappings of the routing table as correspondingto the indicated source node; determining, by the user terminal routingsystem, whether the corresponding mapping is presently enforcedaccording to a validity window associated with the identified one of themappings; and updating the corresponding mapping according to thereceived forward-link data only when the corresponding mapping is notpresently enforced.
 50. The method of claim 0, wherein at least one ofthe mappings indicates a return-link destination Internet-protocol (IP)address, and further comprising: generating at least one of the mappingsby: determining, by the user terminal routing system, a content hostcorresponding to the return-link destination IP address; identifying apre-stored association between the content host and a routing network ofthe plurality of networks; and generating the at least one mapping toassociate the return-link destination IP with the identified routingnetwork.
 51. The method of claim 0, wherein the determining comprisesperforming a reverse domain name server (DNS) lookup.
 52. The method ofclaim 0, wherein the reverse DNS lookup is performed by the userterminal routing system as a background task concurrently with theidentifying and the routing.
 53. The method of claim 0, wherein therouting table is a preloaded table with a plurality of preloadedmappings prior to the receiving.
 54. The method of claim 0, wherein eachof at least a portion of the preloaded mappings is preloaded by:selecting one of a plurality of pre-stored associations between acorresponding content host and a corresponding one of the plurality ofnetworks; performing a domain name server (DNS) lookup to determine adestination Internet protocol (IP) address associated with thecorresponding content host; and generating the preloaded mapping toassociate the corresponding one of the plurality of networks with arouting table entry comprising the destination IP address.
 55. A userterminal routing system comprising: a local network interface operableto couple with a local user network; a hybrid network interfacecomprising a plurality of network interfaces, each operable to couplewith a respective one of a plurality of communications networks of ahybrid network having different network characteristics; a routing tablehaving stored thereon populated with a plurality of mappings that eachassociate a destination node associated with return-link data with oneof the plurality of communications networks; and a routing state machinecoupled between the local network interface and the hybrid networkinterface, the routing state machine comprising a routing state outputcomputed according to the routing table in response to receivingreturn-link data via the local network interface, such that: thereceived return-link data indicates a destination node corresponding toan identified one of the mappings, and the routing state output directsrouting of the received return-link data over a selected one of theplurality of communications networks via the hybrid network interface inaccordance with the identified one of the mappings.
 56. The userterminal routing system of claim 0, further comprising: a routing tableupdater coupled between the hybrid network interface and the routingtable, and having an update output generated according to forward-linkcommunications received via at least one of the plurality of networks,at least some of the mappings updated in response to the update output.57. The user terminal routing system of claim 0, wherein: the updateoutput is generable in response to receiving forward-link data flows viathe hybrid network interface, each forward-link data flow indicating arespective source node and received via a respective one of thecommunications networks, such that each of the at least some of themappings is updated according to a respective one of the receivedforward-link data flows to map the respective source node with therespective one of the communications networks.
 58. The user terminalrouting system of claim 0, wherein: the update output is generable inresponse to receiving control messages via one of the plurality ofnetworks, the control messages indicating respective routing tableupdates, such that each of at least some of the mappings is updatedaccording a respective routing table update.
 59. The user terminalrouting system of claim 0, wherein each FLCS identifier comprises anInternet protocol address.
 60. The user terminal routing system of claim0, wherein: the state machine comprises a stored routing rule-base thatdefines a set of routing criteria and an alternate network of theplurality of networks, such that, in accordance with whether the set ofrouting criteria is met, the routing state output direct routing of thereturn-link data either over the one of the plurality of networks mappedin the routing table to the destination node of the return-link data orover the alternate network.
 61. The user terminal routing system ofclaim 0, wherein: the stored rule-base defines respective validitywindows for at least some of the mappings; and the routing state outputdirects routing of the return-link data further according to therespective validity windows.
 62. The user terminal routing system ofclaim 0, wherein the routing table comprises a plurality of preloadeddefault mappings.
 63. The user terminal routing system of claim 0,wherein the local user network comprises at least one customer premisesequipment (CPE) device.
 64. A hybrid communications network comprising:a plurality of communications networks; a plurality of user terminalrouting systems, each coupled between the plurality of communicationsnetworks and a respective local user network, each comprising a routingtable having stored thereon a plurality of mappings that associate adestination node for return-link data with one of the plurality ofcommunications networks; and wherein each user terminal routing systemoperates to receive return-link data from its respective local usernetwork, the received return-link data indicating a destination nodecorresponding to the destination node of an identified one of themappings, and to route the received return-link data over a selected oneof the plurality of communications networks via the hybrid networkinterface in accordance with the identified one of the mappings.
 65. Thehybrid communications network of claim 0, wherein the plurality ofcommunications networks comprises a satellite communications network,and a terrestrial communications network.
 66. The hybrid communicationsnetwork of claim 0, further comprising: a provider-sider core noderemote from the user terminal routing systems and coupled with theplurality of communications networks, wherein the routing table ispopulated according to forward-link communications received from theprovider-side core node.
 67. The hybrid communications network of claim0, wherein: the routing table is updated at least in part according toforward-link data flows received via the hybrid network interface, eachforward-link data flow indicating a respective source node and receivedvia a respective one of the communications networks, such that each ofthe at least some of the mappings is updated according to a respectiveone of the received forward-link data flows to map the respective sourcenode with the respective one of the communications networks.
 68. Thehybrid communications network of claim 0, wherein: the routing table isupdated at least in part according to control messages received via oneof the plurality of networks, the control messages indicating respectiverouting table updates, such that each of at least some of the mappingsis updated according a respective routing table update.
 69. The hybridcommunications network of claim 0, wherein: each user terminal routingsystem operates to route the received return-link data further inaccordance with a stored routing rule-base that defines a set of routingcriteria and an alternate network of the plurality of networks, suchthat, in accordance with whether the set of routing criteria is met, therouting of the return-link data is either over the one of the pluralityof networks mapped in the routing table to the destination node of thereturn-link data or over the alternate network.
 70. The hybridcommunications network of claim 0, each routing table comprises aplurality of preloaded default mappings.